<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Compilation with Visual Studio .NET 2003</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><meta name="keywords" content="Intellon, Atheros, Qualcomm, HomePlug, powerline, communications, INT6000, INT6300, INT6400, AR7400, AR7420"><link rel="home" href="index.html" title="Qualcomm Atheros Open Powerline Toolkit"><link rel="up" href="ch03.html" title="Chapter 3.  Software"><link rel="prev" href="ch03s06.html" title="Cross-Compiling on GNU/Linux"><link rel="next" href="ch03s08.html" title="Microsoft Solution Files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">
				Compilation with Visual Studio .NET 2003
				</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s06.html">Prev</a> </td><th width="60%" align="center">Chapter 3. 
		Software 
		</th><td width="20%" align="right"> <a accesskey="n" href="ch03s08.html">Next</a></td></tr></table><hr></div><div class="section" title="Compilation with Visual Studio .NET 2003"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="software-visualstudio"></a>
				Compilation with Visual Studio .NET 2003
				</h2></div></div></div><p>
				To build the <span class="application">Open Powerline Toolkit</span> on Windows XP, you must have access to a Windows computer with  <span class="application">Visual Studio .NET 2003</span> and <span class="application">WinPcap</span> runtime libraries installed. <span class="application">WinPcap</span> is an open source version of the packet capture library, <span class="application">libpcap</span>, widely used on <span class="application">Linux</span> and <span class="application">OpenBSD</span> systems. It is readily available on the Internet. Installation of these components is beyond the scope of this document. 
				</p><p>
				The Windows and Linux versions of the <span class="application">Open Powerline Toolkit</span> use the same code base but the Windows version requires a Microsoft solution file that includes special compiler settings and specific POSIX header files. The solution file and header files are included in the same archive as Linux version.
				</p><div class="example"><a name="idp20839248"></a><p class="title"><b>Example 3.4. 
					Microsoft Visual Studio .NET 2003
					</b></p><div class="example-contents"><div class="mediaobject" align="center"><img src="VisualStudioNET.png" align="middle"></div></div></div><br class="example-break"><p>
				Use an application like <span class="application">WinZip</span> to extract archived files into a build folder of your choice. Use <span class="application">Windows Explorer</span> to locate solution file <code class="filename">.\VisualStudioNET\plc-utils.sln</code> under the toolkit root folder. Double-click the file to open it with <span class="application">Visual Studio .NET</span>. In <span class="application">Visual Studio .NET</span>, open the <code class="option">Solution Explorer</code> window and observe a display similar to that shown above. 
				</p><p>
				Figure 1 illustrates a <span class="application">Visual Studio .NET</span> window with the <code class="option">Solution Explorer</code> pane exposed. In the <code class="constant">Solution Explorer</code> window, <span class="command"><strong>right-click</strong></span> the <code class="constant">plc-utils</code> solution and select the <code class="option">Rebuild</code> menu option. Compiliation should begin. Watch for comilation errors.
				</p><p>	
				On successful compilation of all projects in this solution, you should find executable programs in the <code class="filename">Release</code> folder under each project folder. If not then look in the <code class="filename">Debug</code> folder,  instead. You can now open a console window, change to each <code class="filename">Release</code> or <code class="filename">Debug</code> folder in turn and run the programs located there. Instead, we recommend that you create a <span class="application">Windows Installer</span> package by <span class="command"><strong>right-clicking</strong></span> on the <code class="constant">Install</code> project in the <code class="constant">Solution Explorer</code> window and selecting the <code class="option">Build</code> menu option. Compilation should resume.
				</p><p>
				On successful completion of the install project build, you should find the <span class="application">Windows Installer</span> file <code class="filename">plc-utils.msi</code> in the <code class="filename">VisualStudioNET</code> folder above the <span class="application">install</span> project folder. Double-clicking on this file will start the <span class="application">Windows Installer</span> program.
				</p><p>
				To distribute the toolkit package to other Windows computers,  copy the <span class="application">Windows Installer</span> file to a public network share or some type of portable media.
				</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s06.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s08.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
				Cross-Compiling on GNU/Linux
				 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 
					Microsoft Solution Files
					</td></tr></table></div></body></html>
